System and method for modeling, monitoring and managing telecommunications networks and infrastructure

ABSTRACT

An analyzing a telecommunications network that receives environmental data, vendor data, and customer data related to a telecommunications transaction. A telecommunications transaction identifier is generated for each telecommunications transaction to determine attributes associated with each telecommunications transaction. The telecommunications transaction identifier and the attributes associated with the identified telecommunications transaction are mapped to a customer-specific parameter. The telecommunications network determines whether the transaction conforms to the parameters.

BACKGROUND OF THE INVENTION

This invention is directed to a methodology and system for monitoringthe use of telecommunications equipment across a network, and inparticular, for monitoring and graphically representing usage compliancewith vendor and customer rules.

Today's telecommunication systems foster an environment ofmisinformation, inaccuracies, and complexity that are at best difficultand at worst impossible to manage. Current telecommunicationsenvironments are made up of multiple legacy systems that have been patchworked together throughout the years. This has provided an environmentwhere errors and inconsistency are prevalent but difficult to identifyand resolve. This enables an environment that lacks controls, managementand visibility. Vendors provide application such as AT&T BusinessDirect®, Sprint FONVIEW®, AT&T Bill Management System®, Sprint PCS EBT®,Nextel Smart CD+®, Verizon PerspectivePlus® and others. Theseapplications provide only basic querying capabilities and do not provideany graphical representation of the network, its uses or mechanisms toestablish customer specific business rules and/or parameters.Additionally, they only represent data and information from the specificvendor and do not provide for the integration of data for multiplevendors into a single source.

BRIEF SUMMARY OF THE INVENTION

A system for modeling and managing a telecom network includes a serverhaving a database. The server receives and normalizes customer data fromvarious sources. The server stores the data in the database. The dataincludes information identifying customer characteristics anddemographics; vendor services and characteristics and environmental datathat define the characteristics and attributes of the customertelecommunications infrastructure. The data is normalized andcategorized across key service categories such as, local, long-distance,data, Internet and mobile. The server generates multiple reports andgraphic representations of the telecommunications infrastructure andusage as a function of the information. The reports provide capacity(usage), cost information, compliance/audit (contract and policy) andallows for analysis across vendors and services. Once logged in to theserver all reports and analytics are available across alltelecommunications services.

In a preferred embodiment, the server receives environmental data,vendor data, and customer data related to a telecommunicationstransaction. The server generates a transaction type identifier for eachtelecommunications transaction. The server determines attributesassociated with each telecommunications transaction and maps thetransaction type identifier and the associated attributes to acustomer-specific parameter group and based on this information,determines whether the transaction type identifier and attribute conformto the parameters; i.e., is telecommunication usage in compliance withthe expected parameters.

In another embodiment of the invention, the server receives vendor datarelated to a customer telecommunications transaction and determinesattributes associated with each telecommunications transaction. Based onthe information, the server generates a graphic representation of acustomer telecommunications infrastructure as a function of the vendordata. The graphic representation is then validated utilizingenvironmental data and customer data received at the server.

Additionally, the application provides for billing based on performancedata and baseline information gathered at time of input/loading. Theserver then generates billing/invoicing based upon on establishedcriteria.

BRIEF DESCRIPTION OF THE DRAWINGS

For a fuller understanding of the invention, reference is had to thefollowing description taken in connection with the accompanying drawingsin which:

FIG. 1 is a schematic drawing of a system constructed in accordance withthe invention;

FIG. 2 is a flow chart of the process for receiving source data,transforming, normalizing and generating outcomes and reports inaccordance with the invention;

FIG. 3 is an operational diagram of the transformation and normalizationprocess in accordance with the invention;

FIG. 4 an exemplary representation of a graphic representation of thenetwork in accordance with the invention; and

FIG. 5 is schematic data level representation of the transformation andnormalization of source vendor data in accordance with the invention.

DETAILED DESCRIPTION OF THE INVENTION

A user, typically a company or other organization, utilizes a variety oftelecommunications products and services such as Internet, intranet,local access networks and wide area networks, by way of example. Eachmay be provided by different vendors, each with their own rules andconditions regarding both usage and business terms. The products andservices may include one or all of landline telephones, cellulartelephones, Internet communications (both between computers andvoiceover Internet protocols), and personal digital assistants such asBlackberry®, iPhone® or the like.

A system, generally indicted as 25, as shown in FIG. 1, is an exemplaryschematic representation of a system in accordance with an embodiment ofthe invention that graphically represents the system for monitoring andmanaging telecommunications infrastructure. A server 45 receives datafrom multiple sources; telecommunications service and equipment vendors20, environmental information (information that is complementary and notnecessarily coming directly from the vendor or the customer, such ascentral office locations, service types, locations types, customeraddress validation, and the like by way of non-limiting example) 10 andtelecommunications customer information 30, and stores all necessarydata and information to perform an application 40 at server 45 in adatabase 42 associated with server 45. The application 40 normalizes thedata and information for loading into database 42. The storedinformation is then analyzed by server 45 utilizing application 40 tocreate multiple reports 60,70,80, and graphic outputs 50. These reportscorrespond in one embodiment to four major categories and/or functions;graphic representation (graphic representation of the customer'stelecommunications network and associated transaction key attributes)50, controls (audit and contract compliance) 60, performance (keyperformance and operational metrics/indicators) 70, and management(policy adherence, compliance and planning information) 80.

Reference is now made to FIG. 2 in which a method in which server 45performs application 40 in accordance with the invention is provided. Anoperational system is established. Database 42 provides the structurewithin system 25 to store the processed data and generate the normalizedinformation model in application 40. Input sources vary depending oncustomer data 30 and vendor data 20. Each vendor has parametersassociated with its service and contract, which are unique to the vendorat least in part. Similarly, customer data 30 is unique in part to thecharacteristics of a customer's physical and operational infrastructureand the customer's usage.

The process for establishing reports is started in a step 101. Onparallel tracks, data is input to server 45 to be operated on byapplication 40. On one track, customer and vendor demographics 30, 20and environmental information with respect to the vendors and thecustomer are input. They may be input manually in a step 103 through thesubmission of questionnaires to the customer and/or vendor, interviewsand surveys of customer and/or vendor. The type of information solicitedmay be, by way of non-limiting example, the locations of parts of the ITinfrastructure of the customer, responsible persons for reporting,billing and oversight of the network, or the like. The manual input isperformed in step 103.

Simultaneously, or in parallel with the step 103, information may beuploaded electronically through interfaces and electronic sources suchas magnetic tapes, CABs, electronic bills, and EDI. With the appropriateinterfaces, the electronic bills for a particular customer from eachvendor may be directly electronically downloaded in step 105. In step107, both of these types of data are loaded onto server 45 through adesignated interface.

Once data is gathered from the various sources in step 107, the data isnormalized and transformed in a step 109 utilizing application 40 instep 111 and as shown in more particular detail in FIG. 3. As a preludeto step 109, source data 20 from a variety of vendors A-C is received ina step 205 (FIG. 3). This data is transformed and normalized by applyingdeveloped logic that resolves the multiple data entities 20,30 from theindividual vendors and customers who are dependent on the vendor and/ortypes of services provided. A unique telecommunication transaction IDthat identifies the specific detailed telecommunications transaction andservice is generated as a function of vendor information 20 and customerinformation 30.

The normalization process begins by identifying the vendor in a step 210and the service type supplied by that particular vendor in a step 215.It is determined whether or not the service is mobile, long distance(LD) or fixed (all remaining types of service). In a step 225, therequired data entities for vendor and service are obtained from theinput information. The data entities are those characteristics orparameters explained below which are associated with the vendor productsand services.

Reference is now made to FIG. 5, wherein a schematic diagram of the datanormalization tables, which are created in accordance with theinvention, are provided. Vendor data 510 is collected from the dataentry steps 103, 105 and 107. Vendor data 510 includes substantially allrelevant information from the vendor including bill identification, thecall types provided by the vendor for that particular service, theoriginating place and termination place allowed by the vendor, circuitinformation, tax information, any sales or discount rates, start timesand end times for the service, and the contract ID, by way of example.However, not all of the information is required for each type of serviceor telecommunication product. Therefore, in step 225, the vendor data isscreened as it applies to the various types of services; long distance,land and mobile, to create loaded transaction tables 340. These tablescontain the vendor parameters associated with specifictelecommunications transaction types.

Each communication and event such as a phone call, a page, or an e-mailcommunication is identified as a distinct telecommunication transaction.In other words, a transaction corresponds to each discreet use of atelecommunication or service by the customer/end user for which a vendorcharges the customer. The data entities required to process atransaction are culled from vendor data 510 and are normalized in step109 to form loaded transaction tables 530. The loaded transaction tablesinclude the vendor information, telecommunication transaction IDs andattributes.

In a step 230, a telecommunication transaction ID is generated frominput vendor information such as the customer bills. Thetelecommunication transaction ID is transaction-type specific, notcustomer- or vendor-specific to allow grouping and comparisons oftransactions across customers and vendors. As seen from exemplarytransaction IDs 550, a code is created or adopted as the ID. The IDs550, preferably are functional in that they describe a telecommunicationtransaction type, such as DOSDIRA, which corresponds to domesticoutbound service directory assisted. In comparison, SISFL may stand forstate inbound switched Florida. It should be noted that standard IDssuch as USOC codes may be adopted as the IDs 550.

All transactions have attributes 560. Where IDs 550 are genericidentifiers for a class of telecommunications transaction, attributes560 are specific information associated with each transaction.Attributes 560 as shown in exemplary transaction IDs 550 may include aseries of numbers corresponding to the circuit number, the call date,the duration, the charge amount, the origination and termination numbersor any personal identification number (PIN) associated with the specifictelecommunications transaction. In step 235 the telecommunicationstransaction ID codes 550 are mapped and stored with the attributes 560associated with that transaction.

As previously stated, in a step 103, vendor, customer and environmentaldata had been entered, stored, and loaded onto server 45. As a result,contract tables 570 are created which are a representation of theexpected terms of the contract covering any service or product which inturn covers each telecommunication transaction. The table elements mayinclude information such as the transaction rates, the discount, and anylimitations on the type of transactions, such as after a certain date inwhich the contract has lapsed or before a certain date in which thecontract does not come into effect, or calls at restricted originationsor terminations such as impermissible foreign calls.

Therefore, in a step 240, each telecommunication transaction andassociated attribute 560 is mapped against the input data in table 570for validation and compliance and the mapped data is loaded intoapplication 40 in step 111. Environmental data includes the locations atwhich products are used or services are provided. A customer physicalinfrastructure map is created.

In step 240, the transaction data is also compared to the physicalinfrastructure as input in step 103 as environmental information 10 todetermine whether legitimate locations are involved in thetelecommunication transaction.

Returning to FIG. 1 in a step 113, an analysis report is executed andgenerated. There are varieties of reports, which may be generated instep 113. There are performance reports 70 (performance reports 70include compliance), there is the graphic representation of the networkreport 50, there are the controls report 60, and there is a report frommanagement which is a management report 80.

In a step 115, utilizing the normalized data, performance and compliancereports 70 are generated. The performance and compliance reports may beutilized in a step 120 to determine whether in fact use of thetelecommunications network complies with the parameters of thecontrolling contracts. By comparing the contract table values 570 withthe report based upon the telecommunication transaction identification550 and attributes 560 loaded as transaction table 530 in database 42, acomparison is made to determine whether or not there are anydiscrepancies. If there are no discrepancies then the process for thatreport is over. If there is a discrepancy, then in a step 123 claims aregenerated to be transmitted to the vendor and work orders as a functionof stored customer policies are generated in a step 125. The claims andwork orders become action items, which are monitored in a step 127. Step127 can be done manually or by server 45 with “tickles” and “updates”and reminders to both the vendor and the customer until it is determinedin step 129 whether the action item has been resolved.

If the action item has been resolved or completed then the outcomes areloaded into a model 131, the outcomes provide updated information,establishing an accurate representation of the telecommunicationsinfrastructure and its operational and contracted parameters, which isloaded into server 45 as a feedback and background to generate furtherreports as part of process 111. If the action item has not beencompleted or resolved, then it is continued to be monitored in step 127until resolution.

Utilizing the environmental data gathered in step 103 and the dataentities for each vendor in a step 225, and the tables 510, 530 createdin step 225, a graphic representation of the customer telecommunicationsinfrastructure with attributes 560 is created as shown in FIG. 4.

A simplified network is shown in FIG. 4 to facilitate discussion. Thegraphic representation 300 is a graphic representation of the entiretelecommunications infrastructure serviced by application 40. Eachfacility 350 represents a physical customer facility location at whichcontracted telecommunication equipment and services are utilized. Itcould be an office building or a customer employee home where Internetand cellular phone services are utilized. In a preferred embodiment,different icons may be used to correspond to different types offacilities. Service relationship 330, i.e., type of service such asPrimary Rate Interface (PRI), Terrestrial Interoffice Facility Level 1(T-1), Internet Protocol Multiprotocol Label Switching (IP MPLS),Asynchronous Transmission Mode (ATM), Frame Relay (FR), Metro Ethernetand the like are shown. The graphic representation is based upon vendorinformation 20 and environmental information 10 input in step 103, 105and culled in steps 225 and 240. The relationships are graphically shownas connections between appropriate facilities 350. Furthermore, the keyattributes and environmental information for each facility may begraphically represented as text 310. This may include the location type,the physical address of the location, the service types and relevantattributes for each transaction. The location type may be a user home, acentral office, a satellite office or the like. The cost for runningeach facility may also be presented.

This data may be utilized as the baseline report in a step 119. It maythen be used to measure performance, either initially or through laterreports in step 119. This baseline is used in order to make a model ofthe entire network and input into the model in a step 131 and then isthen loaded into server 45 to refine the analysis and reports generatedin step 113.

The performance and compliance report generated in a step 115, thegraphic report generated in a step 117, and the baseline and performancedata generated in a step 119 are analyzed in a step 121 to produceperformance report 70 and controls report 60 (this analysis may be donemanually or automated). These reports contain performance metrics to becompared against. established targets and best practices. Controlreports would provide data that would be validated (test compliance)against. external contracts and service level agreements (vendors), andinternal policies and service level agreements.

The controls and performance reports are utilized to update a modelgenerated in step 115 in a step 125 so that the model keeps refiningitself. The performance and control reports will allow for refinement oftargeted and expected results; redefining and reevaluating targets,defining new more impactful measures, additional compliance testing (newpolicies or redefined business rules)

By analyzing the network on a transaction-by-transaction basis, alongwith key attributes and characteristics, the model and system allow forthe preparation for in depth analyses across multiple perspectives, suchas services, vendors, usage, locations and the like. By providing agraphic representation of the analysis, manual analysis, understandingand correction are expedited.

While the present invention has been described with reference toexemplary embodiments, it is to be understood that the invention is notlimited to the disclosed exemplary embodiments. The scope of thefollowing claims is to be accorded the broadest interpretation so as toencompass all modifications, equivalent structures and functions of therelevant exemplary embodiments.

Thus, the description of the invention is merely exemplary in natureand, thus, variations that do not depart from the gist of the inventionare intended to be within the scope of the exemplary embodiments of thepresent invention. Such variations are not to be regarded as a departurefrom the spirit and scope of the present invention.

What is claimed as new and desired to be protected by Letters Patent ofthe United States is:
 1. A method for analyzing a telecommunicationsnetwork comprising the steps of: providing a server and a remotecomputer; the server receiving environmental data, vendor data, andcustomer data related to a telecommunications transaction, theenvironmental data including infrastructure information; the servergenerating a telecommunications transaction identifier for eachtelecommunications transaction as a function of at least one of thevendor data and the customer data; the server determining attributesassociated with each telecommunications transaction as a function of atleast one of the customer data and the vendor data; the serverdetermining a customer infrastructure information as a function of theenvironmental data; mapping the telecommunications transactionidentifier and the attributes associated with the identifiedtelecommunications transaction to a customer-specific parameter, thecustomer specific parameter including the customer infrastructureinformation; the server generating a graphic representation of aphysical customer infrastructure and the attributes including agraphical representation of at least one service relationship between afirst facility and an at least a second facility as at least oneconnection between the first facility and at least second facility; theserver utilizing the graphic representation to determine whether thetelecommunications transaction conforms to the customer specificparameters; and transmitting the graphic representation to the remotecomputer.
 2. The method for analyzing a telecommunications network ofclaim 1, wherein environmental data includes at least one of vendoroffice locations, customer locations, and service types.
 3. The methodfor analyzing a telecommunications network of claim 1, furthercomprising the step of obtaining required data entities for the vendorand generating the transaction type identifier as a function of therequired data entities.
 4. The method for analyzing a telecommunicationsnetwork of claim 3, further comprising the steps of: determining thecustomer specific parameter from the required data entities; creating acontract table for a transaction; and comparing the telecommunicationstransaction identifier and the associated attributes to the parametersin the contract table to determine whether the telecommunicationstransaction conforms to the parameters.
 5. The method of analyzing atelecommunication network of claim 4, further comprising the steps of:generating a work order when the telecommunications transaction does notconform to the parameters and transmitting the work order to a vendorassociated with the telecommunications transaction.
 6. The method ofanalyzing a telecommunication network of claim 1, wherein thetelecommunication transaction identifier identifies the type oftelecommunications transaction identified.
 7. The method of claim 1,wherein the graphic representation includes a first icon and at least asecond icon, the first icon graphically representing the first facilityand the at least second icon graphically representing the at leastsecond facility.
 8. The method of claim 7, wherein the servicerelationships are shown as connections between the first icon and the atleast second icon.
 9. The method of claim 1, wherein the graphicrepresentation includes key attributes and environmental informationassociated with a facility, graphically represented as text adjacent arespective icon.
 10. The method of claim 1, wherein the graphicrepresentation includes text corresponding to key attributes andenvironmental information.